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

No annotations are provided, so the description carries the burden of behavioral disclosure. It indicates this is a retrieval operation ('get'), but does not elaborate on return format, error behavior, authentication needs, or any other side effects. The term 'full details' is vague and could be more informative.

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 immediately states the action and includes a useful usage pointer. Every word earns its place; there is no redundant or empty phrasing.

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?

Despite being a simple one-parameter tool, the description lacks an output schema and does not describe the content of 'full details.' An agent would not know what fields to expect in the response. The purpose and usage are clear, but the lack of return-value information makes it incomplete for a tool with no output schema.

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 100%, so the parameter 'id' is already well-documented in the schema. The description adds only marginal value by calling it a 'profile ID' and referencing search_trucks, which mirrors the schema's own description. This meets the baseline without adding significant extra meaning.

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 tool's function: getting full details on a specific verified food truck by profile ID. It uses a specific verb/resource combination and distinguishes itself from sibling tools like search_trucks (search) and list_marketplace (list) by being a direct ID lookup.

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 explicitly says 'Use after search_trucks to get more detail on a specific result,' which gives clear context on when to invoke it. However, it does not mention when not to use it or explicitly name alternatives, so it falls just short of a 5.

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