igdb_get_company

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It merely states 'Get' without mentioning that this is a read operation, that authentication is required (client_id/client_secret parameters), or any side effects. The description lacks transparency about auth needs and what changes occur.

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 a single sentence that conveys the core functionality. It is concise and front-loaded, but could include additional context (e.g., auth) without becoming verbose. It is efficient but slightly terse.

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 no output schema and no annotations, the description should compensate by explaining the return value, authentication requirements, and parameter behavior for client_id and client_secret. The current description is too minimal for a tool with four parameters, leaving gaps in understanding.

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 description mentions 'by name or ID', which corresponds to the name and company_id parameters. However, client_id and client_secret are not explained in the description or schema (schema coverage 50%). The description adds minimal meaning beyond the schema; a baseline 3 is appropriate.

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 clearly states the verb 'Get', the resource 'a game company from IGDB', and the lookup methods by name or ID. It distinguishes from sibling tools like igdb_get_game (game) and igdb_search_games (search), making the tool's purpose specific and unambiguous.

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 implies when to use (when you have a name or ID) and the two modes. It does not explicitly state when not to use or provide alternatives, but the context of sibling tools makes the usage clear. A more explicit note about prerequisites (like authentication) would improve this.

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