get_company_blueprint_certification_candidate

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

Annotations already establish read-only, idempotent, and non-destructive behavior, which the description does not contradict. The description adds useful scope context with 'one exact' and 'whole-company,' clarifying this is a single-record point read rather than a search or list, but it does not detail error cases, auth needs, or operational quirks.

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, front-loaded sentence with no filler or repetition. Every word earns its place, and the core action and scope are immediately visible.

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 simple exact-get tool, the output schema and annotations cover return values and safety behavior, reducing the burden on the description. However, the absence of usage differentiation and parameter semantics leaves some contextual gaps, making this a minimum-viable definition rather than a fully self-sufficient one.

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%, and the description does not explicitly explain company_ref, project_ref, or candidate_id. The parameter names and the phrase 'one exact...candidate' imply candidate_id is the target identifier and the refs provide parent context, but the description does not compensate for the absent schema documentation.

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 identifies a specific verb ('Read'), a specific resource ('whole-company certification review candidate'), and a precise cardinality ('one exact'). This implicitly distinguishes it from list-style or proposal-style siblings like propose_company_blueprint_certification, and from the golden-loop candidate variant.

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 gives no guidance on when to use this tool versus siblings such as get_current_company_blueprint_certification or get_golden_loop_certification_candidate. The verb 'Read' implies retrieval, but there are no exclusions, prerequisites, or alternative routing hints.

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