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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds the context that the returned data is the current profile used for matching. For a zero-parameter read operation this is adequate, though no additional behavioral specifics (e.g., staleness, auth, empty profile behavior) are disclosed.

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?

One compact sentence with no filler. The key facts (view action, profile resource, matching-contract purpose) are front-loaded and every word earns its place.

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 parameterless read-only tool with annotations covering safety and no output schema, the description supplies the necessary purpose and context. There is no missing information that would prevent an agent from invoking it correctly.

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 zero parameters, so schema description coverage is complete and there is nothing for the description to add. Per the 0-parameter baseline, this is a clean score; the description reinforces that no inputs are needed.

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 uses a specific verb ('View') and specific resource ('your current business profile') and adds purpose ('being used to match contracts'). This clearly distinguishes it from the write-oriented sibling set_business_profile and other opportunity/contract tools.

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 'being used to match contracts' implies the tool is appropriate when an agent needs to inspect the active matching profile, but there is no explicit when-to-use versus alternatives or exclusion criteria. The alternative set_business_profile is never referenced, so guidance is only implicit.

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