Get org chart as PNG

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the HTTP method and authorization class ('board_or_agent'), which is useful but doesn't disclose other behavioral traits like caching behavior, rate limits, or that the output is a binary image. With annotations covering the basics, the additional value is moderate.

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 very concise at two lines. The first line repeats the title, which is somewhat redundant but acceptable. The second line provides technical details (endpoint, auth class). No filler, but the structure could be more integrated. Overall efficient.

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?

Given that an output schema exists, the description doesn't need to detail return values. However, it fails to mention that the tool returns a PNG image (implied by title but not explicit). With one parameter and many siblings, more context (e.g., output is an image file, not URL) would improve completeness. Some gaps remain.

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?

Schema description coverage is 0%, so the description must compensate. However, it merely restates the path ('companyId') without explaining what companyId is, its format, or its role. No parameter semantics are added beyond the schema structure.

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 explicitly states 'Get org chart as PNG', which is a specific verb-resource pair with format indication. The title reinforces this, and the endpoint path clarifies the resource. It is clearly distinguished from siblings like pc_get_companies_by_company_id_org (JSON) and pc_get_companies_by_company_id_org_svg (SVG).

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 over alternatives. It mentions authorization class but does not indicate when PNG format is preferred over SVG or JSON. No explicit comparison or usage context is given.

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