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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description only needs to add context beyond that. It does so by describing the profile fields returned and the dependency on a prior search_graph result. It does not mention possible operation behaviors like rate limits or result size, but the safety profile is already captured and the description is accurate to those annotations with no contradiction.

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?

Two sentences, no fluff. The first sentence contains the action and output outline; the second contains the call trigger and dependency. Every sentence serves a purpose with no redundant phrases.

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 description is well-formed for a read-only retrieval tool with annotations for safety. It gives the trigger and bound key, name and dependency and enough content in terms of what is returned. Since there is no graph known, it could be a little more explicit about how graphId coordinates with nodeId, but the schema fills most of that gap.

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 baseline under the rubric is 3. The description repeats the node_id prerequisite that is also well documented in the schema (node must come from prior search result), but adds no meaning beyond the schema. graphId and userId are not described in the description, but the schema itself carries enough.

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 starts with a clear action and resource: "Get the full profile of a specific trend" and then enumerates the content returned (description, lifecycle stage, signal strength, geographic scope, and properties). It clearly differentiates from sibling tools by placing this as the deeper detail tool that operates on a trend node from search_graph, not on earnings, labels, capabilities, or other resources.

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?

Explicit usage guidance is present: "Use when you need deeper detail on a single trend after search_graph returned a summary." It also states the prerequisite: "Requires node_id from a prior search_graph result," which tells an agent when it is appropriate and what it needs before invoke. This is far beyond a mere hint.

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