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

No annotations are provided, so the description carries the burden of disclosing behavior. It does indicate a read-only 'Return' operation and specifies the content returned, which is useful. However, it does not disclose potential errors, permissions, freshness of facts, or any other behavioral caveats, leaving the agent with only a minimal behavioral picture.

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 well-structured sentence that leads with the action and object. It contains no filler or redundant phrasing, making it appropriately concise and easy to parse for an AI agent.

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?

For a tool with only one required parameter and no output schema, the description is reasonably complete in stating what the tool returns. However, it lacks essential detail about the 'ref' parameter and does not clarify the output structure or when to prefer this over get_entity, so it is only minimally viable.

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 required parameter 'ref' with no description, and schema description coverage is 0%. The description does not explain what 'ref' should refer to, such as whether it is an ACEL identifier, a source reference, or some other key. Because there is no parameter documentation, the description needed to compensate but does not.

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 states a specific verb ('Return') and a specific resource ('source-linked evidence and current facts supporting an ACEL entity representation'), which makes the tool's purpose fairly clear. It distinguishes itself from search-oriented siblings, though the term 'ACEL entity representation' is somewhat jargon-heavy and could be clearer.

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 phrase 'supporting an ACEL entity representation' implies the tool is for retrieving evidence/facts behind an entity, but there is no explicit when-to-use guidance or mention of alternatives such as get_entity.js. Usage is implied rather than explained, so an agent must infer when this is the correct tool.

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