get_company_profile

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description 'Show company profile' is consistent with the annotations (readOnlyHint=true, destructiveHint=false), but it adds no extra behavioral context such as expected return format, pagination, or auth requirements. With annotations already covering the safety profile, the description contributes nothing beyond what is already declared.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, consisting of a single short phrase 'Show company profile'. It is front-loaded and free of unnecessary words, which is good, but it may be too terse to convey full purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one parameter and clear annotations, but the description lacks context about when to use this tool instead of the sibling 'list_company_profiles'. It does not mention that it retrieves a single profile by ID, nor does it describe any behavior beyond the basic operation. This omission leaves a gap for users unfamiliar with the API.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one parameter 'profile_id' with a description ('the id of the company profile'), and schema description coverage is 100%. The tool description does not add any further parameter semantics; it merely says 'Show company profile' without referencing the parameter. The schema already provides the necessary meaning, so this is adequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Show company profile' uses a clear verb and resource, indicating a read operation to fetch a company profile. However, it does not differentiate itself from the sibling tool 'list_company_profiles', which likely lists multiple profiles, so it lacks explicit distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of 'list_company_profiles' for retrieving all profiles, nor any prerequisites or context for using this tool. The user must infer from the tool name that it retrieves a single profile by ID.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.